-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.13.0 #11
0.13.0 #11
Conversation
|
||
this._listenValuePrev = value; | ||
|
||
this.updateDisplay(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added these checks while testing a three.js example that had an uncheckable checkbox with listen()
. I thought listen()
was causing the checkbox to lose interactivity by updating the display every frame. The author's intent was actually to disable the controller by using a setter that could ignore assignment calls.
This code appeared to "fix the bug" because the value of input.checked
would be allowed to change, while in truth it was out of sync with getValue()
, and was never forced to updateDisplay()
because the actual value never changed between frames.
Public facing changes: https://github.com/georgealways/lil-gui/blob/dev/Changelog.md#0130
Internal changes:
scripts/tests.js
was getting too big. Now it's split into separate files under thetests
dir._initInput
and_initSlider
were cleaned up to be more consistent.